Search Results

Standard

DEFINITION OF STANDARD INTERFACES FOR GALLEY INSERT (GAIN) EQUIPMENT PHYSICAL INTERFACES

2015-11-23

CURRENT

ARINC810-5

ARINC 810 defines galley equipment physical attachments, envelopes, connections, and qualification guidelines for interchangeable galley equipment. Supplement 5 defines a size 6 galley insert, intended for microwave oven installation and other equipment suited to this type of installation. Supplement 5 also clarifies reference dimensioning for all GAIN sizes defined by ARINC 810.

Standard

CABIN EQUIPMENT INTERFACES PART 9 CABIN INTERFACE NETWORK (CIN)

2015-11-20

CURRENT

ARINC628P9-4

ARINC 628, Part 9 defines general architectural philosophy and aircraft infrastructure for the proper use and interface of various cabin information network related equipment. It specifies a generic on-board infrastructure with commercial server technology, high-speed data communication and exchange via wired and wireless LAN for a wide range of applications. Supplement 4 defines web-based interfaces for cabin control panels and recognizes current standards for commercial browsers and applications. It incorporates current network security practices, including reference to ARINC 842 Digital Certificates.

Standard

AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 1 REQUIRED SERVICES

2015-08-21

CURRENT

ARINC653P1-4

This standard defines a general-purpose Application/Executive (APEX) software interface between the Operating System of an avionics computer and the application software. The interface requirements between the application software and operating system services are defined in a manner that enables the application software to control the scheduling, communication, and status of internal processing elements. Supplement 4 adds multicore processor service capabilities.

Standard

AVIONCS APPLICATION SOFTWARE STANDARD INTERFACE PART 2 EXTENDED SERVICES

2015-08-21

CURRENT

ARINC653P2-3

As avionics software continues to evolve, so does ARINC Specification 653. ARINC 653 Part 2 specifies extensions (i.e., optional services) to the required Application Program Interfaces (APIs) described in ARINC 653 Part 1. Supplement 3 adds optional multicore services capabilities.

Standard

AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 0 OVERVIEW OF ARINC 653

2015-08-03

CURRENT

ARINC653P0-1

This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Supplements to Parts 1 through 5 will be made more consistent with Part 0 in conjunction with the technical changes expected to be made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 - Overview of ARINC 653, Part 1 - Required Services, Part 2 - Extended Services, Part 3 - Conformity Test Specification, Part 4 - Subset Services, and Part 5 - Core Software Required Capabilities. Supplement 1 reflects the introduction of multicore processor support in Parts 1 and 2.

Standard

GUIDANCE FOR TOOL AND TEST EQUIPMENT (TTE) EQUIVALENCY

2015-08-01

CURRENT

ARINC735B-2

This document defines a Traffic Surveillance capability for NextGen and SESAR airspace environments. Supplement 2 adds hybrid surveillance functionality. It satisfies recent updates to FAA Airworthiness Circular AC 20-151B - Airworthiness Approval of Traffic Alert and Collision Avoidance Systems (TCAS II), and Technical Standard Order TSO-119d requiring the annunciation of a hybrid surveillance failure. Supplement 2 also adds strobe program pinning, updates TCAS inputs status, improves aircraft troubleshooting, and supports recent central maintenance computer function block point updates.

Standard

AIRCRAFT SOFTWARE COMMON CONFIGURATION REPORTING

2015-07-31

CURRENT

ARINC843

This standard defines a common configuration report format that can be retrieved from an aircraft for use by ground tools and maintenance personnel. Reports will be generated in Extensible Markup Language (XML) format and structured as defined by this document. Several optional elements and attributes are defined to allow flexibility for a given report. This standard provides aircraft manufacturers, regulatory agencies, and airlines a format standard for aircraft configuration reporting, and facilitates automated comparison of configuration data reports (e.g., authorized versus as flying, etc.).

Standard

LOGICAL SOFTWARE PART PACKAGING FOR TRANSPORT

2015-07-31

CURRENT

ARINC641

The purpose of this standard is to provide a method for packaging aircraft software parts for distribution using contemporary media or by electronic distribution. This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. This standard format can be then stored or distributed on a single physical media member (CD-ROM), or by electronic crate. The obsolescence of floppy disks drive an urgent need for this guidance.

Standard

CABIN EQUIPMENT INTERFACES PART 0 CABIN MANAGEMENT AND ENTERTAINMENT SYSTEM - OVERVIEW

2015-07-27

CURRENT

ARINC628P0-3

The purpose of this document is to provide an introduction and overview of the ARINC 628 series of Specifications. ARINC 628 defines equipment and installation standards for cabin equipment, which is generally defined as communication and entertainment equipment designed for passenger use. Part 0 provides the concepts and overview of ARINC 628 and descriptions of each individual part. Appendix B is written in briefing chart format to facilitate the user in preparing quick-reaction overhead projection-type presentations. Supplement 3 represents a summary of recent changes to Parts 1 through 9 of ARINC Specification 628.

Standard

INSTALLATION STANDARDS FOR LOW FREQUENCY UNDERWATER LOCATOR BEACON (LF-ULB)

2015-07-15

CURRENT

ARINC677

This document provides aircraft installation requirements for a Low Frequency Underwater Locator Beacon (LF-ULB) transmitting on a frequency of 8.8 kHz. ICAO Annex 6 Amendment 36, states that a LF-ULB shall be installed on all aircraft with a maximum certified take-off mass of over 27,000 kg, operating over water at particular distances to land suitable for making an emergency landing. ICAO Annex 6 Amendment 36 further states that an LF-ULB shall be installed by January 1, 2018.

Standard

GENERAL STANDARDIZATION OF CAN (CONTROLLER AREA NETWORK) BUS PROTOCOL FOR AIRBORNE USE

2015-07-15

CURRENT

ARINC825-3

This document defines Controller Area Network (CAN) interface standard. It defines the physical layer provisions to maintain compliance with ISO 11898. The scope of Supplement 3 is limited to correcting the high integrity message CRC calculation and providing additional guidance to support interoperability. This includes the definition of a periodic health status message, functional status reporting, peer-to-peer message structure, and quiet bus behavior.

Standard

SPECIFICATION CONNECTORS, RACK AND PANEL, RECTANGULA REAR RELEASE CRIMP CONTACTS

2015-06-01

CURRENT

ARINC404B-2

This document defines standardized connectors intended for use on rack-mountable avionics equipment. It is aligned to the latest version of MIL-C-81659. Supplement 2 was updated to support cabin equipment applications. It corrects intermateability control dimensions that are provided for single shell plug connectors.

Standard

ADVANCED FLIGHT MANAGEMENT COMPUTER SYSTEM

2014-12-15

CURRENT

ARINC702A-4

The Advanced FMCS provides expanded functions beyond that defined in ARINC 702 to support the anticipated requirements for operation in the CNS/ATM operating environment. GNSS and RNP based navigation, air-to-ground data link for communications and surveillance, and the associated crew interface control/display definitions are included.

Standard

FUNCTION DEFINITION OF AIRBORNE MANAGER OF AIR-GROUND INTERFACE COMMUNICATIONS (MAGIC)

2014-12-12

CURRENT

ARINC839

This standard defines an Internet Protocol (IP)-based communication management function for data communications called the Manager of Air/Ground Interface Communications (MAGIC). This standard recognizes that the number of available off-board communication links is expanding (e.g., broadband satellite, broadband terrestrial, Gatelink), and that each link may be provided by a different service provider. In addition, each link may be available to the aircraft in specific flight phases and in specific geographic locations. As the industry continues to increasingly embrace IP-based communications, there is reason to define an aircraft routing function that provides standardized access by all aircraft subnets to available communication links.

Standard

CABIN CONNECTORS AND CABLES, PART 2, SPECIFICATION OF CONNECTORS, CONTACTS, AND BACKSHELLS

2014-10-07

CURRENT

ARINC800P2

This specification describes the general connectors, contacts, and backshells in their shape and characteristic for cabin systems for commercial aircrafts. ARINC 600, ARINC 404, and ARINC 801 connector specifications are published as independent standards.

Standard

STANDARD DATA INTERFACE FOR GALLEY INSERT (GAIN) EQUIPMENT PART 1 CAN COMMUNICATIONS

2014-08-26

CURRENT

ARINC812AP1-1

The purpose of this specification is to define the general Galley Insert (GAIN)standardization philosophy, provide comprehensive equipment interfaces, and disseminate the most current industry guidance. Part 1 covers the Controller Area Network (CAN) data interface attachments, envelopes, and data content to be considered between all galley equipment using a Galley Data Bus as described within this specification. This document is intended as the successor and replacement for ARINC Specification 812. This document contains significant improvements to CAN data interfaces.

Standard

3GCN - SEAT DISTRIBUTION SYSTEM

2014-08-15

CURRENT

ARINC809-3

This specification defines general architectural philosophy and specific design guidance for the proper installation and interface of various cabin equipment within the seats. Consistency with this specification allows each component installed on the seat to operate in concert when integrated with other relevant cabin type equipment. Standard electrical and mechanical interfaces of the In- Flight Entertainment System (IFES) equipment for the 3rd Generation Cabin Network (3GCN) associated with the seat are defined. This equipment consists of the headphone jacks (HPJ), passenger control unit (PCU)/multi function handset (including the cord), seat video display (SVD), remote data outlet (RDO), integrated seat box (ISB) which includes the seat power box (SPB)/seat data box (SDB), remote power outlet (RPO), and in-seat cables. Appropriate definitions are also provided for other electrical devices associated with the seat control/position mechanism.

Standard

AIRCRAFT INTERFACE DEVICE (AID)

2014-07-15

CURRENT

ARINC759

This document sets forth the characteristics of an Aircraft Interface Device (AID) intended for installation in commercial aircraft. The intent of the document is to provide general and specific design guidance for the development of an AID for use in retrofit applications associated with aircraft typically developed between the mid-1970s through the 1990s, that primarily utilize ARINC 700 series avionics, and that interface with the aircraft via ARINC 429 and ARINC 717 unidirectional buses and Hi/Lo discrete signals. This document describes the desired operational capability of the AID and the standards necessary to ensure interchangeability.

Standard

HANDHELD MICROPHONE AND BOOM MICROPHONE

2014-01-15

CURRENT

ARINC538C

This document describes the aircraft industry recommendations for a handheld microphone and boom microphone for use with airborne radio installations. This document, ARINC Characteristic 538C, is in addition to and does not supersede the older ARINC Characteristic 538B: Hand-Held Microphone, dated February 16, 1983.

Standard

AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE, PART 3A, CONFORMITY TEST SPECIFICATION FOR ARINC 653 REQUIRED SERVICES

2014-01-13

CURRENT

ARINC653P3A

The scope of this Compliance Test Specification is to define test procedures to demonstrate compliance of the API behavior only. This does not include performance tests (e.g., benchmark tests), nor demonstration of capability of the operating systems to manage combinations of configuration parameters.